Gateway device for machine-to-machine communication with dual cellular interfaces

ABSTRACT

Gateway devices can use dual cellular interfaces to provide reliable communications for client machines. A gateway device can use one of the dual cellular interfaces as a primary interface and the other as a hot backup interface. The backup interface remains connected to a cellular network while communications are routed on the primary interface. Accordingly, the gateway device can rapidly switch communications between from the primary interface to the backup interface. Applications, for example, for ATM payment processing, vending machine telemetry, point of sale payment processing, kiosk internet connectivity, remote monitoring and control, mobile or electronic health, and remote information displays, may run on the gateway devices, on servers, on user devices, or a combination of these devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/257,548, filed on Jan. 25, 2019 and entitled “Gateway Device for Machine-to-Machine Communication with Dual Cellular Interfaces,” which is a continuation of U.S. patent application Ser. No. 15/627,206, filed on Jun. 19, 2017 and entitled “Gateway Device for Machine-to-Machine Communication with Dual Cellular Interfaces,” issued Jan. 29, 2019 as U.S. Pat. No. 10,194,340, which is a continuation of U.S. patent application Ser. No. 15/046,876, filed Feb. 18, 2016 and entitled “Gateway Device for Machine-to-Machine Communication with Dual Cellular Interfaces,” issued Jun. 20, 2017 as U.S. Pat. No. 9,686,184, which is a continuation of U.S. patent application Ser. No. 14/255,827, filed Apr. 17, 2014 and entitled “Gateway Device for Machine-to-Machine Communication with Dual Cellular Interfaces,” issued Apr. 5, 2016 as U.S. Pat. No. 9,307,344, which claims the benefit of U.S. provisional patent application Ser. No. 61/813,066, filed Apr. 17, 2013 and entitled “Gateway Device for Machine-to-Machine Communication with Dual Cellular Interfaces,” each of which are hereby incorporated by reference.

BACKGROUND

The present invention generally relates to the field of communication systems and more specifically to systems and methods for machine-to-machine communication with dual cellular interfaces.

The use of machine-to-machine (M2M) systems has and will continue to increase. Machine-to-machine systems may also be referred to as the Internet of things. Communications between devices in a machine-to-machine system can use a gateway device. In addition to providing communications, the gateway device may provide additional service is such as running applications. Present gateway devices may have shortcomings; for example, in some circumstances their communications may not be sufficiently reliable.

SUMMARY

In an aspect, a gateway device is provided. The gateway device includes: a first cellular communication module configured to communicate with a first cellular network; a second cellular communication module configured to communicate with a second cellular network; at least one local communication module configured to communicate with one or more client machines; and a processor coupled to the first cellular communication module, the second cellular communication module, and the at least one local communication module, the processor arranged for operating one of the first cellular communication module or the second cellular communication module as a primary interface and the other one of the first cellular communication module or the second cellular communication module as a hot backup interface to route communications with one or more client machines.

In another aspect, a method for use in providing machine-to-machine communications for a client machine using a gateway device having a first cellular communication module operable to communicate with a first cellular network and second cellular communication module operable to communicate with a second cellular network is provided. The method includes: selecting one of the first cellular communication module or the second cellular communication module as a primary interface and the other one of the first cellular communication module or the second cellular communication module as a backup interface; routing communication with the client machine over the primary interface while maintaining the backup interface actively connected to its respective cellular network; monitoring communications on the primary interface; determining whether communication with the client machine should switch from the primary interface; routing communication, after determining that communication with the client machine should switch from the primary interface, with the client machine over the backup interface.

In another aspect, a gateway device is provided. The gateway device includes: a first network communication module configured to communicate with a first network; a second network communication module configured to communicate with a second network, wherein one of the first network communication module or the second network communication module is a primary interface and the other one of the first network communication module or the second network communication module is a hot backup interface; at least one local communication module configured to communicate with one or more client machines; a route switch module configured to route communications with one or more client machines over the first network communication module or the second network communication module.

Other features and advantages of the present invention should be apparent from the following description which illustrates, by way of example, aspects of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of the present invention, both as to its structure and operation, may be gleaned in part by study of the accompanying drawings, in which like reference numerals refer to like parts, and in which:

FIG. 1 is a block diagram of a communication system using a gateway device with dual cellular interfaces according to a presently disclosed embodiment;

FIG. 2 is a functional block diagram of an gateway device according to a presently disclosed embodiment;

FIG. 3 is a flowchart of a process for managing communications on dual cellular interfaces according to a presently disclosed embodiment; and

FIGS. 4 and 5 are diagrams of a gateway device from a family of gateway devices according to a presently disclosed embodiment.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with the accompanying drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in simplified form in order to avoid obscuring such concepts.

The present disclosure describes a family of gateway and router devices. The devices can be used to provide reliable communication for payment transactions. The devices may be referred to as gateway devices, SysLINKs, SmartHubs, or Systech Financial Gateways (SFGs). Other applications for the gateway devices include secure cellular and Internet access for ATM payment processing; vending machine telemetry; point of sale (POS) payment processing and internet connectivity; kiosk internet connectivity, remote monitoring and control; mobile or electronic health; and remote information displays. Gateway devices also support home and building security and automation applications. Further applications include mobile merchants, mall kiosks, major events, seasonal sales, outdoor markets, etc. The applications may run on the gateway devices, on servers, on user devices, or a combination of these devices.

FIG. 1 is a block diagram of a communication system using a gateway device with dual cellular interfaces according to a presently disclosed embodiment. The gateway device 110 communicates with a first cellular network 121 and a second cellular network 122, for example, to provide services that allow payment transactions to succeed with a high degree of probability. The first cellular network 121 and the second cellular network 122 may be independent mobile networks. The services may have associated SLAs (service level agreements) that guarantee service characteristics (e.g., delays, frequency and duration of outages). For payment transactions, availability of services can be of particular importance. In other systems, one or both of the first cellular network 121 and the second cellular network 122 may be a non-cellular network; for example, the gateway device 110 may communicate using DSL, DOCSIS, MMDS, WiMAX, or other technologies.

The gateway device 110 communicates via a local network 140 with various machines. The machines that communicate with the gateway device 110 using the local network 140 may also be referred to as client machines, client devices, or clients. In the example system of FIG. 1, the client machines that communicate with the gateway device 110 include a personal computer 151, a thermostat 152, an alarm 153, and an automatic teller machine (ATM) 154. Some of the devices may be collocated; for example, the gateway device 110 may be located in the automatic teller machine 154. The local network 140 may be, for example, a wired network such as Ethernet, a wireless network such as Wi-Fi, or a combination of networks.

FIG. 2 is a functional block diagram of a gateway device according to a presently disclosed embodiment. The gateway device of FIG. 2 can be used to implement the gateway device 110 of the system of FIG. 1. The gateway device of FIG. 2 includes a processor module 225. The processor module 225 is coupled to a first cellular communication module 211, a second cellular communication module 212, a wired communication module 241, a wireless communication module 242, and a memory module 235.

The first cellular module 211 and the second cellular module 212 are configured to transmit and receive communications with cellular networks. For example, the first cellular module 211 may communicate with the first cellular network 121 via communication link 131 and the second cellular module 212 may communicate with the second cellular network 122 using communication link 132. The first cellular module 211 and the second cellular module 212 may also be referred to as network communication modules. In alternative embodiments, the network communication modules may use communication technologies other than cellular. For example, a network communication module may communicate using DSL, DOCSIS, MMDS, WiMAX, or other technologies. Additionally, a network communication module may use a local network connection (e.g., an Ethernet connection) to another device that then communicates with an Internet service provider, wide area network, or some other network. The cellular interfaces may use different underlying technologies, such as PPP, LTE, CDMA, and EVDO. The first cellular module 211 and the second cellular module 212 may use subscriber identification module (SIM) cards to identify and authenticate the gateway device to the cellular networks. The gateway device may, accordingly, have two SIM card slots.

The gateway device can provide connections to the Internet for machines that communicate with the gateway device via the wired communication module 241 or the wireless communication module 242. The wired communication module 241 or the wireless communication module 242 may also be termed local communication modules. The gateway device provides the connections to the Internet using the first cellular module 211 and the second cellular module 212. The gateway device includes one or more antennas for transmission and reception of radio signals.

The wired communication module 241 and the wireless communication module 242 are configured to transmit and receive communications with client machines. In the system of FIG. 1, for example, the wired communication module 241 may communicate with the automatic teller machine 154 and the personal computer 151 and the wireless communication module 242 may communicate with the thermostat 152 and the alarm 153.

The processor module 225 can process communications being received and transmitted by the gateway device. The memory module 235 stores data for use by the processor module 225. The memory module 235 may also be used to store computer readable instructions for execution by the processor module 225. The computer readable instructions can be used by the processor module 225 for accomplishing the various functions of the gateway device. The memory module 235 or parts of the memory module 235 may be a non-transitory machine readable medium. For concise explanation, the gateway device or embodiments of it are described as having certain functionality. It will be appreciated that in some embodiments, this functionality is accomplished by the processor module 225 in conjunction with the memory module 235, and the communication modules. Furthermore, in addition to executing instructions, the processor module 225 may include specific purpose hardware to accomplish some functions.

The gateway device may perform operations to enhance reliability of communications with the devices connected to the gateway device. For example, the gateway device can monitor and analyze the reliability of communications with the first wireless network 121 and the second wireless network 122 and switch between them accordingly.

The first cellular module 211 and the second cellular module 212 may also be termed network interfaces. The gateway device can operate one of the network interfaces as a primary interface while the other network interface is operated as a hot backup (or “secondary”) interface. The two network interfaces may, for example, connect to different cellular service providers. The first cellular module 211 and the second cellular module 212 may be physically separate modules or may be a single module with dual cellular interfaces.

The use of two cellular interfaces can greatly improve the availability of communication services. That is, the gateway device may determine that communication on one of the interfaces is unavailable or unreliable and switch to using the other interface. Usage of the two cellular interfaces may also be based on other criteria, for example, cost of the corresponding cellular data plans.

FIG. 3 is a flowchart of a process for managing communications on dual cellular interfaces according to a presently disclosed embodiment. The process may be performed by the gateway device of FIG. 2. The gateway device can have two network interfaces active simultaneously. Although both network interfaces are active, only one network interface is ordinarily used for network traffic and the other network interface is idle. Alternatively, the gateway device may operate with only the network interface used for routing communications active. Whether the network interface that is not used for routing communications is active or passive may be configured by a user. By having two cellular interfaces connected, the gateway device can switch between the interfaces with little delay. In the system of FIG. 1, for example, the gateway device 110 may be operating with communication link 131 to the first cellular network 121 as the primary interface and communication link 132 to the second cellular network 122 as the backup interface. The default route may be through the primary interface. Alternatively, the default route may use the last interface that was active.

In step 310, the gateway device 110 monitors the primary cellular interface. For example, periodically the gateway device 110 may test the primary interface to be sure network traffic is still occurring.

If the process determines, in step 320, that the gateway device should stop using the primary interface, the gateway device switches, in step 330, the default route to the hot backup interface; otherwise, the process returns to step 310 to further monitor the primary cellular interface. The process may determine that that the gateway device should stop using the primary interface when network traffic on the primary interface is not occurring. Switching cellular interfaces may be termed failover. Similarly the used of dual cellular networks may be referred to as wireless redundancy.

The gateway device can use one or more monitors, for example, a session monitor module 231 and a transaction monitor module 232, to test the interfaces. The monitoring of step 210 may be performed, for example, by the session monitor module 231, the transaction monitor module 232, or a combination of the session monitor module 231 and the transaction monitor module 232. The session monitor module 231 and the transaction monitor module 232 can signal a route switch module 233 to change which cellular interface communications are routed over. The session monitor module 231, the transaction monitor module 232, and the route switch module 233 may be software modules that are stored in the memory module 235 and executed by the processor module 225.

The gateway device can be used as a router to provide general access to the Internet. Accordingly, the gateway device can act as the DHCP (dynamic host configuration protocol) server for client machines. Static IP support is also provided. When the default route is switched, the gateway device can also update DNS (domain name system) information so that DHCP client machines observe minimal delays in the network traffic. The gateway device maintains the network interface specific DNS information for the primary and backup interfaces and acts as a DNS proxy for the DHCP client devices. In this way, the appropriate DNS server is used when switching between the primary and secondary interfaces. These functions may be performed by the route switch module 233.

After switching to the hot backup interface in step 330, the gateway device monitors, in step 340, the primary interface to determine, step 350, whether the gateway device should return to using the primary interface. The process may determine that that the gateway device should return to using the primary interface when network traffic resumes on that interface. The monitoring in step 340 may be the same or similar to the monitoring performed in step 320.

The gateway device may determine that network traffic has resumed on the primary interface by various methods. For example, the primary interface may be assumed to have network traffic if a connection can be completed to a server, such as a payment processor. The server may be identified by an IP (internet protocol) address. Testing the primary interface for network traffic can be performed on a periodic basis while the hot backup interface is being used. The gateway device can use a Systech Online Update Protocol (SOUP) update or Light Weight Heartbeat (LWHB) feature to periodically check for SOUP configuration updates. If a permanent change to the designation of the primary/hot backup interfaces is required, the LWHB can also be used.

If the process determines, in step 350, that the gateway device should return to using the primary interface, the gateway device switches, in step 360, the default route to the primary interface; otherwise, the process returns to step 340 to further monitor the primary cellular interface. The route switch in step 360 may be performed similarly to the route switch performed in step 330. Step 330 and step 360 may be performed, for example, using the route switch module 233.

The process of FIG. 3 may be modified, for example, by adding, altering, or reordering steps. Additionally, steps may be performed concurrently. Additional criteria for switching network interfaces may be used. For example, the gateway device may switch interfaces to reduce cost. In an embodiment, in step 350 the process may determine whether to return to using the primary interface based on monitored performance of the backup network rather than the primary network. Additionally, both the primary interface and the backup interface may be monitored concurrently with route switching based, for example, on relative performance of the two interfaces.

The gateway device can provide usage logging to show when each interface is in use. The logging may include, for example, the absolute time of switch and accumulated times on each interface. Some of the logging information may be kept local to the gateway device and other logging information may be transmitted to a server. For example, the absolute time may only be available in the local log for use in troubleshooting.

The designation of which interface is the primary interface and which interface is the hot backup interface can be done, for example, through a gateway device configuration file. SOUP update or LWHB can be configured to periodically test for updates to the configuration file, including designation of the primary interface. The configuration file may also be able to change one or more parameters of the monitors. Information about the configuration and usage of the interfaces may also be logged.

The gateway device of FIG. 2 may use various methods for monitoring the cellular network interfaces. The monitoring methods may be used in the process of FIG. 3. Two methods are described below. The session monitor method checks network packet counts. The transaction monitor method checks attempted connections to external servers. The session monitor method may be performed by the session monitor module 231. The transaction monitor method may be performed by the transaction monitor module 232.

When using the session monitor method, the gateway device is not involved in packet traffic, unlike transaction based processing. Accordingly, the gateway device cannot guarantee transactions, but can monitor network traffic and switch interfaces based on the monitored network traffic. The amount of monitoring may be determined, for example, based on the SLA. Excessive monitoring may cause increased data charges on the cellular network. Under monitoring may not meet customer SLA needs.

The session monitor method checks receive and transmit packets on the primary interface. If there are many transmit packets and few receive packets, the session monitor can ping the DNS server on the primary interface. In an embodiment, the ping occurs when the number of transmit packets is much greater (e.g., by a factor of two) than the number of receive packets. If ping fails, the session monitor may determine that network traffic is not occurring on the primary interface and signal a route switch. If both transmit and receive packets are zero, it does not necessarily indicate that network traffic is not available. Thus, the session monitor may have a timer to ping the DNS server periodically (e.g., once an hour). The session monitor may also use determination of a ping response failure time (when the DNS server is unreachable) that is excessive to determine that network traffic is not available. The period of the session monitor and the interface switching time determines the worst-case downtime. For example, if the session monitor runs every minute, the ping failure time is 1 second, and the interface switch time is 2 seconds, the maximum downtime is 63 seconds. The session monitor may use alternate methods besides ping to determine whether network traffic is occurring on the primary interface. For example, several connection tests (connecting to a server, ping, and DNS lookup) may be given a weighted value. The weighted values may be based, for example, on policies for individual users. Once the weighted value exceeds some threshold, the gateway device would perform the switch to the hot backup interface. These policies can be customizable based on particular use cases.

The gateway device may take advantage of local services on the gateway device like SOUP or LWHB to trigger the route switch if a failed connection is detected by any of these services. For example, if the gateway device is processing transactions, and the transaction fails, this can trigger the route switch. Using just the session monitor, any particular transaction (e.g., a POS (point-of-sale) transaction or ATM transaction) is not guaranteed; however, general connection to the Internet can be achieved.

The transaction monitor can track outbound connections from the gateway device. The transaction monitor may use, for example, specialized code that runs as a kernel driver monitoring network traffic. This code can be configured to track outbound connections attempted to specific ports on specific external servers (e.g., a payment processor site). More specifically, the transaction monitor can detect TCP (transmission control protocol) SYN/ACK handshakes for one or more IP addresses. If a failed connection is detected, a signal is generated to switch network interfaces. The transaction monitor continues to check for failed connections to the payment processor. Any failed connections while on hot backup may be ignored or could trigger a switch back to the primary interface. The transaction monitor method may, in some embodiments, provide a better way to increase the probability that POS or ATM transactions to a specific payment processor will succeed. However, general access to the Internet may not be improved over the session monitor method since only specific ports and servers are monitored.

The gateway device, in an embodiment, may use the session monitor and the transaction monitor at the same time. Either monitor can trigger a switch to the hot backup interface. Additionally, a change to the configuration file on the SOUP server will be detected by SOUP update or LWHB, which may result in a change of the primary/hot backup interface designation.

The gateway device configuration file provides a method, among other things, to switch the primary/hot backup priority. Which interface is preferred may be changed, for example, to take advantage of potential cost differential between two carriers associated with the cellular interfaces. The configuration file determines which interface is primary and which is the hot backup. Additionally, the configuration file can contain timer information related to the monitor periods. This configuration file is typically updated on a 24 hour cycle. Through the use of the Light Weight Heartbeat (LWHB), this time period can be reduced. For example, the gateway device can be configured to use LWHB to check every 15 minutes against the SOUP server. If the primary/hot backup needs to be switched, the LWHB would indicate a full check-in is needed, resulting in an updated configuration to the gateway device.

Additionally, the gateway device can record the usage of the primary and hot backup interfaces and upload this information to the SOUP server on a period (e.g., daily cycle).

The gateway devices can operate in many scenarios. In a first example usage case, a network operator (e.g., a mobile virtual network operator (MVNO)) wants to change the order of preference of network use, making the current primary network the secondary network and vice versa. The network operator may want to do this for a subset or for the entire universe of dual network gateway devices that the network operator uses. In this example usage case, this is a permanent change rather than a temporary change, for example, because of network session failure or transaction failure. The network operator also wants to be able to change other configuration file settings.

The network operator can achieve the change in order of preference of network use my multiple methods. In a first method 1, the SOUP server is used to change the preference in the configuration file for the primary and hot backup interfaces, making Carrier 1 the hot backup and Carrier 2 the primary network. The gateway device can be configured for the SOUP update or LWHB to periodically contact the SOUP server for a configuration update.

A second example usage case illustrates a scenario where a transaction fails. Here, the transaction monitor signals a route switch so that the hot backup interface is used rather than the primary interface. When the primary network recovers (e.g., as determined by a ping test or connection to the payment processor) the primary network interface is again used.

The gateway device of FIG. 2 and the related methods and communication systems are susceptible to many variations. Additionally, for clear and brief description, many descriptions of the systems and methods have been simplified. For example, the figures generally illustrate one or a few of each type of device (e.g., two cellular communication modules, one wireless communication module), but a gateway device may have many of each type of device. Similarly, many descriptions use terminology and structures of a specific wireless standard. However, the disclosed systems and methods are more broadly applicable.

Implementations of a gateway device may include many features in addition to those described above. In various embodiments, gateway devices and the systems in which they are used may include various combinations of hardware/firmware features, cloud-based and local server features, and smart phone features.

Examples of hardware/firmware features include: hardware upgrade slots that support cellular modules and/or other hardware options and future hardware features; support for 2G through 4G (e.g., CDMA, EVDO, LTE, GSM, 1×RTT, SPA+) cellular performance or other future cellular technologies; one or multiple Ethernet ports (e.g., using wired communication module 241 or the like), with multiple independent IP addresses when the gateway device has more than one Ethernet port; zero or multiple POTS (plain old telephone service) ports (e.g., v.90, v.92); zero or multiple serial ports (with RS232, RS422 and/or RS485 physical interfaces) that may be configured as standard serial ports (for applications such as POS and security) or as DEX & MDB ports (for vending applications); zero or multiple USB (universal serial bus) ports; zero or multiple microSD (or other types memory card) slots; support for various local wireless technologies including Wi-Fi (e.g., 802.11 a/b/g/n), ZigBee, Z-Wave, Bluetooth, NFC, ANT, etc.; temperature and motion sensors; zero to multiple connectors for external general purpose 10 using a GPIO and/or I²C interface; an external or internal backup battery; and support for local applications.

Examples of cloud-based and local server features include: provisioning; configurable alerts (for reporting errors, location, motion, battery status, etc.); Wi-Fi hotspot; a consumer quality GUI for status and control; vending software; building security software; and an object oriented GUI interface that can be used by an unsophisticated user.

Examples of smart phone features (which may be used with other user devices, e.g., tablet and notebook computers) include: a web-driven GUI interface; and a custom app-driven GUI interface.

Gateway device may be provided in many product configurations. A family of gateway device products includes multiple enclosures that provide maximum flexibility in providing multiple configuration options. The specific options which are enabled for any one configuration can be controlled by the physical presence of the hardware features or can be set, locally or remotely, by electronic configuration, which is independent of the actual presence of physical hardware. The number of different hardware configurations may be established based on economies of scale through manufacturing of standardized configurations balanced by the additional costs which will be driven by the presence of some unnecessary hardware for specific configurations.

An example gateway device family includes four subfamilies: The SysLINK 1000 is a low cost, single purpose gateway that will typically be used for simple bridging applications as well as for simple ATM or vending applications. A SysLINK 1000 will generally be placed near the target application. The SysLINK 2000, SysLINK 3000 and SysLINK 4000 are all fully featured general purpose gateways, bridges or routers that support the connection of multiple devices across multiple local or remote networks. They are used in multi-purpose home and building applications and often placed in a central location (such as a wiring closet) with home runs to the target applications. The family of gateway devices can support combinations that include multiple local network connections and multiple broadband networks for internet connectivity. The gateway devices may be co-located with other gateway devices of the same or different subfamilies. Across subfamilies, the gateway devices may have substantially the same appearance, although the physical dimensions of the devices may vary, for example, driven largely by the number of communication interfaces that are provided by a particular device.

Gateway devices may be provided with various levels of communications performance. Many applications for gateway devices require data rates that are no higher than 0.05 Mb/s (megabits per second). This is well within the range that is supported by 2G cellular technology. However, other applications require faster performance, which can be provided by 3G or 4G cellular technology. For example, kiosks, home gateways and digital signage applications may require real-time multimedia streaming.

The architecture of the gateway devices, in an embodiment, is designed to permit field upgrade of an installed device from a slower speed technology to a higher speed technology or the addition of an additional network module by a user with little or no training. This architecture has been constructed to accept cellular modules from multiple sources with minimal development. The architecture supports future cellular technologies as well as the existing technologies previously mentioned.

Some bridging applications do not use cellular connectivity (such as Wi-Fi to Ethernet). In these applications, performance will match the underlying physical interface and will be minimally throttled by the gateway device.

Example applications for gateway devices include: ATMs with non-GPS (global positioning system) based location services and motion detection (including tilt) that will provide alerts (e.g., page, text, MSG, email, tweet, audible alarm, etc.) for unauthorized motion; ATMs with GPS based location services, motion, and temperature sensing; ATMs bundled with Wi-Fi hotspot services with GPS based location services, motion, and temperature sensing; home and building automation for lights, locks, HVAC (heating, ventilation, and air conditioning), and smart grid energy monitoring, controlled through a smart phone application; vending services with support for credit card transactions and inventory monitoring; security services; video surveillance; environmental or security alarm box monitoring; fax gateway; and building services with pool/spa, irrigation, and alarm monitoring.

Gateway devices may connect to different types of servers via the Internet or other networks. A wide variety of client machines, such as utility meters, telephones, kiosks, smart phones, thermostats, facsimile machines, motion sensors, and alarms may be connected to one gateway device. Each of these devices could be connected through a different, normally incompatible, network. The gateway device can be used to communicate information to and from those devices that have been coupled to the gateway to one or more Internet-based servers. An individual can access the information, for example, via a notebook, smart phone, desktop or tablet computer.

Gateway devices can be provided in many physical forms. In various embodiments, gateway devices have the following physical features or subsets thereof. Devices may be placed on a flat surface (desk, shelf, etc.), wall mounted, rack mounted, and/or magnetically mounted to a metal surface. A gateway device may have one or more I/O connections and/or power inputs on the rear of its enclosure. Lights and buttons may be facing the front. One or more antennas, when present, may be attached to both sides of the gateway device gateways and may be user adjustable, for example, up to 270 degrees in three planes.

The power input may be drawn from an AC outlet or from a DC source, for example, 4.5 V to 30 V DC. The power input can use a locking power connector to provide increased reliability. Devices may include a recessed reset push button facing the front of the unit. Additional antennas for other wireless communication modules may be located inside the enclosure. The gateway may include SMA female and SMA male connectors for external antennas to support various wireless communication technologies. Devices will support the use of a SIM card if such a card is necessary to support the underlying cellular technology, for example, for GSM or LTE service. Devices may also use multiple SIM cards. The multiple SIM cards may be used with the same cellular module or with different modules.

The physical enclosure for a gateway device may be physically small to support applications that require an embedded gateway, for example, for ATM, vending and remote display applications.

Some gateway devices may include a display, for example, an LCD or touch screen display. The display can provide a graphical user interface. Some gateway devices may also include an interface, for example, HDMI (High-Definition Multimedia Interface), to an external display.

In various embodiments, the gateway devices include option slots for configuring the devices with a range of features. The option slots may be multiple types and occur in differing number in various family members. A motherboard may, for example, contain functions that are common to all or many member of a family of SysLINK gateways. For example, the motherboard includes a programmable processor for controlling communication operations and directing traffic between cards populating the option slots.

In various embodiments, the SysLINK gateways support Ethernet networks and have the following features or subsets thereof. Ethernet ports may be configured as a secured LAN, an unsecured LAN, or a WAN port. A WAN port connects to an Internet source, such as a broadband router. Such a port may be identified as an “Internet port.” A LAN port connects to a local network, such as an individual Ethernet-based device, a switch, or a router. Ethernet ports may operate at 10, 100, 1000 Mbps speeds or other speeds. One or more of the Ethernet ports may support power over Ethernet (PoE).

The gateway devices include routing functionality to connect the provisioned communication devices. The router functionality includes support for firewall, DHCP, NAT, IPv4, IPv6, VPN pass through, certificate based Open-SSL, VPN, QOS, dynamic DNS, URL filtering, traffic filtering, and port forwarding.

Internet access may be provided by cellular, Ethernet, Wi-Fi, power line communications, satellite, dialup modem, or other communication technologies. Any of these technologies can be designated as a primary or backup connection. For devices with multiple sources of Internet access, the various sources are prioritized. The priority may be set automatically or through user configuration. Gateway devices are able to access a backend server through routers and firewalls. Access to the backend server may be at programmable intervals or as defined by the needs of applications that are being executed. Some gateway devices have an always-on connection to the backend server, allowing random access to such devices from the server. Such an operation may be termed “on-demand.”

In various embodiments, a gateway device may include one or more POTS ports for connections that use traditional analog telephone lines. POTS ports may be used, for example, with FAX or ATM devices. A POTS port may function as a standard phone line from the perspective of appliance that is plugged into the gateway device. Supported MODEM standards include 300 bps: V.21; 1200 bps: V.22 and FastConnect; 2400 bps: V.22bis and FastConnect; 9600 bps: V.29, V.32 and FastConnect; 14,400 bps: V.32bis; 33,600 bps: V.34; 56,000 bps: V.90; V.42bis; and MNP5 data compression. The ports include on and off hook line voltage monitoring, parallel handset (intrusion) detection, V.42 and MNP 2-4 error correction (for example, for dial backup). A POTS port may be used to provide standard Group 3 FAX from 300 to 14,400 bps with Class 1 command compatibility. Higher speeds may also be provided.

One or more of the POTS ports will be able to interface to a standard phone line for remote access and Internet connectivity.

A POTS port supports DTMF (dual-tone multi-frequency, including generation and detection of touch tones), pulse dialing, or relevant FSK (frequency-shift keying) protocols. Functions may be programmed for compatibility with alarm panels and/or other applications.

In various embodiments, a gateway device includes one or more serial port. The serial ports may support RS-232, for example, for alarm systems, RS-422, RS-485, and RS-485/422/232. A serial port may operate in an asynchronous or synchronous mode. A serial port may have either a DCE or DTE physical interface. A serial port may support various protocols including SDLC and 3270 bisync.

In various embodiments, gateway device gateways include one or more USB ports. The USB ports may, for example, be USB 2.0 ports and operate in master mode. A USB port may be used, for example, to connect to memory sticks, cellular modems, PIN terminals, payment terminals, and cameras. A USB port on the gateway may supply power, for example, 500 mA at 5 V, to an attached device. Some of the USB ports are accessible internally, while others are accessible externally to a gateway device. Some USB ports may be directly wired to a USB slave device.

In various embodiments, gateway devices include one or more cellular interfaces. Cellular wireless interfaces may connect to various carrier services, for example, Verizon 2G, 3G, 4G, AT&T 2G, 3G, 4G, and Sprint 2G, 3G, 4G. The cellular wireless interfaces commonly use antennas that are external to the enclosure of the gateway device. Multiple antennas may be used to increase reliability. Multiple antennas may be used to provide multiple simultaneous connections. The gateway device supports location services through cellular services, for example, for use when a GPS location is not available. Multiple cellular interfaces may be provided in one gateway device. In an embodiment, cellular wireless interfaces may be used to communicate with users with the gateway device providing network communications, for example, by a wired backhaul connection.

In various embodiments, gateway devices include Wi-Fi wireless interfaces may operate according to various standards, such as 802.11a, b, g, and n. A Wi-Fi interface may use one or multiple antennas. A Wi-Fi module may support security protocols, such as WAP, WPA, WPA2, and AES, as well as new protocols as they are introduced. When a Wi-Fi wireless interface operates as an access point, multiple (e.g., 16 or 20) simultaneous connections are provided. A Wi-Fi interface may also function as a client device, for example, when providing Internet access to the gateway device. Many other types of wireless interfaces may also be included in a gateway device.

Gateway devices may also provide support for Bluetooth-based devices. A Bluetooth interface may support either the Bluetooth classic or Bluetooth low energy. The Bluetooth network may be used, for example, to communicate data to mobile phones and other Bluetooth devices. Antennas for Bluetooth interfaces are generally inside the gateway device enclosure.

Gateway devices may also provide ZigBee interfaces. Supported specifications include ZigBee Home Automation, ZigBee Smart Energy, ZigBee Telecommunication Services, ZigBee Health Care, ZigBee RF4CE-Remote Control, ZigBee Building Automation, and ZigBee Retail Services. A gateway device with a ZigBee interface operates as ZigBee Coordinator (ZC) and bridges to other networks. Antennas for ZigBee interfaces are generally inside the gateway device enclosure.

Gateway devices may also provide Z-Wave interfaces. Antennas for Z-Wave interfaces are generally inside the gateway device enclosure. Both ZigBee and Z-Wave interface may be joined to and disconnected from other ZigBee and Z-Wave networks. A gateway device may provide simultaneous ZigBee and Z-Wave support to bridge heterogeneous environments.

Support of NFC (near field communication) is also provided. The support is internal to the gateway device in some configurations.

In various configurations, gateway devices include one or more motion detectors. The detectors are sensitive to movement and jostling. Motion detection is used, for example, to detect movement of a machine where the gateway device has been previously installed, for example, inside an ATM. A motion detector may sense general physical movement as well as tilting. A gateway device may provide adjustable alerts when motion is detected. Motion sensitivity may be disabled and re-enabled via a server to allow for legitimate movement of the device.

In various configurations, gateway devices include one or more temperature sensors or interfaces to external temperature sensors. A temperature sensor may have programmable sensitivity in the range of, for example, negative 25 to 100 degrees Celsius. Temperature reading may be provided in Fahrenheit and Celsius. Alerts may be triggered based on set points, such as a minimum temperature and a maximum temperature. An external temperature sensor may be useful for food storage or cold vending machine applications.

In various embodiments, gateway devices include general-purpose input/output (GPIO) interfaces. Such interfaces may be used to interface to smart probes. GPIO interface signals are programmable as inputs or outputs. Some outputs may provide normally open or normally closed connections and may support high voltages, for example, 30 V. This may be used to simulate an open or closed door switch. A GPIO interface signal may also be used to support an analog external temperature sensor, for example, for refrigerated vending applications. GPIO interface signals may also support I²C electrical and messaging protocol. The GPIO interface may be optically isolated. The GPIO interface may also be used to power on or off other devices based, for example, on messages from a server. Other interfaces may also be used to power devices on or off.

In various embodiments, gateway devices include battery backup within the enclosure or, alternatively, support for an external battery backup. The battery backup will power the gateway device for at least one hour. Battery backup may be used to prevent or detect theft or tampering. Status of the battery backup may be reported to a server and may be signaled by indicator lights. Other devices may be connected to the battery backup.

A gateway device generally includes firmware for program storage. Upgrades to the gateway's firmware may, for example, be performed through loading via a portable storage device that can be attached to the gateway device (such as a USB memory stick or a micro SD card); performed over the air via a cellular or Wi-Fi network; performed via an Ethernet connection; or performed by physically changing a storage device in the gateway device.

Many different applications may be provided by the gateway devices and the systems in which they operate. Various applications may operate on the gateway device, on servers communicating with the gateway device, or a combination thereof. Applications may be programmed, for example, via C, C++, or other commonly used languages. Applications may support object oriented GUI interface that can be used by an unsophisticated user to create scripts. This interface may be presented through a web interface and a smart phone.

One type of application is for location information. Location can be derived from one or more tower cells (cell-ID) or through GPS. The device will use the best source, or combination of sources to determine location. Examples of accuracy are tower cells—300 to 2,000 meters and GPS—10 to 300 meters.

A user can specify a geo-fence that will alert if device moves beyond the fence. The geo-fence surrounds a specific area that is defined on a map (and configured via the backend server). Also, the geo-fence can be a circle defined by a radius that is centered at the current location (and configured locally or via the backend server). The radius can be specified, for example, in feet, meters, miles, or kilometers from 0 to 64K.

Location data may be recorded (via a snapshot) once every N seconds, minutes, or hours, for example, configurable from 0 to 1K when the unit is in a “steady-state” operation. Recordings may be stored in non-volatile memory. A device may record, for example, up to 2,880 readings over a user-specified interval (e.g., 1 reading per minute for 24 hours or 1 reading every 10 minutes for 1 week).

A location application may define a “high-threat” operation after motion is detected beyond a configurable threshold. A high-threat warning is enabled for a configurable number of seconds, e.g., from 0 to 64K. During high-threat mode, the location data is recorded (via a snapshot) once every N seconds, minutes, or hours, e.g., configurable from 0 to 1K. The snapshot frequency may be increased during high-threat mode compared to steady-state operation. Recordings are stored in non-volatile memory.

Locations may be reported in batch to the backend server once every N snapshots in steady-state mode. The parameter “N” may be configured from 1 to 1K. Data compression may be used to optimize reporting, especially if no movement is detected.

Another type of application is for alerts. Events or conditions that trigger an alert (such as movement of the device) will produce notifications. The form of notification may be configured for various types of alerts. Examples of responses include one or more notifications via text message, pager or email; a user-programmable C code or GUI script; a phone call with voice prompt, and/or GPIO action (e.g., to trigger a local alarm).

Another type of application is for SmartROAM. Roaming may occur when a device is experiencing difficulty connecting to a local cellular tower (perhaps due to high network congestion, or a weak signal), and the gateway device attempts (if configured) to use another nearby tower even if the alternative tower is with another carrier. The gateway device will attempt to return to the original tower after a wait period. Roaming related events generally do not generate alerts, but may be logged.

Another type of application is for temperature. Temperature measurements may be from on-board temperature sensors or from external probes. The user may specify temperature conditions (e.g., minimum and maximum thresholds) that trigger an event.

Another type of application is for Motion. Motion applications use information from a motion sensor in the gateway device. An example, an application triggers an alert when a motion threshold is exceeded. Thresholds may be, for example, accelerations or orientation angles.

Another type of application is for POS terminals and ATMs. These applications include monitoring the POS or ATM activity, initiating communication to payment processors, and protocol translation for payment processors, activity reporting, etc.

Another type of application is for abnormal transaction patterns. Such applications include generating alerts based on transaction patterns, e.g., a pattern of transaction processing frequency that varies from the norm by more than a threshold.

Another type of application is for video surveillance. Video surveillance applications generally use connectivity to Ethernet or Wi-Fi. Some video surveillance applications stream from a camera to a web-based client or app-based smart phone. Video from multiple cameras may stream simultaneously. Video streams may be filtered to detect predefined conditions in the video. For example, motion detection may trigger recording and an alert notification.

Another type of application is for Wi-Fi hot spots. Features of a hot spot application may include online payment or the use of vouchers, Wi-Fi start page, custom pricing (including free), and complete billing solutions (e.g., payments, refunds, etc.).

Another type of application is for fax. A fax application may provide gateway support to allow an external fax machine connected to a POTS port to send and receive faxes to other fax machines accessible via a phone call. The faxes may be communicated by way of the Internet.

Another type of application is for voice, audio, and/or video. A gateway device may provide voice communication using VOIP technology. The gateway device may include an integral speaker and microphone or may use external devices couple to the gateway device via one of its ports. In some embodiments, video conferencing is also supported. A gateway device may also provide audio and/or video streaming. Additionally, in some embodiments, gateway devices provide PBX functionality to a plurality of users.

A gateway device may also provide content management. For example, the device may provide digital rights management for Kindles, eReaders, iPods, Netflix, Blockbuster, etc. In an embodiment, a user can access cloud-based content via a cellular connection from the gateway device.

A gateway device may also include a media player. The media player may present audio or video via integral devices or by an external device couple to the gateway device, for example, by an HDMI port. The media player can be used for informational displays or marketing messages.

Another type of application is for proximity. A gateway device application may initial actions based on the presence of an individual near the gateway device or within a building or area associated with the gateway device. Uses of proximity applications include security and marketing, such as presenting retail coupons to consumers based on their location. The gateway device, in an embodiment, detects an individual's proximity by communicating with the individual's mobile phone or similar device.

Another type of application is for vending machines. A vending machine application may use, for example, Ethernet, Wi-Fi, and ZigBee interfaces to enable cross-vending machine communication and provide Internet connectivity through one shared connection. Additional vending machine application features include door open, local siren, remote temperature sensor (via the SmartPLUG), and backup battery status. Further vending machine application features include vending status, inventory status, funds reconciliation (e.g., via a cloud-based server, web-based client, and/or smart phone), and credit card and private card payment processing.

In an embodiment, a family of gateway devices shares a modular architecture. Those elements common to each (or most) family members are placed on the main board. Other features and connectivity are handled by the addition of one or more modules. Advantages of this modular approach include the ability to capitalize on new device developments, to incorporate new cellular and/or wireless standards as they are deployed, to simplify configuration control, to minimize SKU growth, to simplify inventory control, and to combine high volume feature clusters in modules to lower cost to selected markets

One such family includes the SysLINK 1000, 2000, 3000 and 4000. These gateway devices include a Systech mother board (SMB). Each SMB has a main processor (e.g., 400 MHz ARM926), RAM (e.g., 256 Mbytes DDR2), flash (e.g., 256 Mbytes), and Ethernet capability. The 1000, 2000, 3000 and 4000 SMBs also contain USB Host connections (e.g., a 4-port hub). These SMBs also have support for motion sensing and internal temperature monitoring. Some features may be depopulated in selected implementations. In an embodiment, the mother board may use multiple physical boards. In some configurations, a gateway device may include a digital storage module, for example, a hard disk drive or a solid state drive. The digital storage module may be used to store, for example, information collected by the gateway device or downloaded information, such as a movie.

Other functions on the SysLINK 1000 through 4000 can be implemented on Systech Option Cards. Systech Option “Cards” mate to the SMB via option “Slots” with 22-pin connectors. Option Cards can be physically mounted on top of the SMB. Any connectors that are necessary to connect external devices are located on the edge of the option card and the rear panel of the gateway device. Some option cards must accommodate wider connectors than others. For instance, DB-25 connectors are wider than DB-9 connectors. To reduce or minimize the gateway device physical size, two different size options slots are defined, full size and half size. Example dimensions for these cards are 56×70 mm (full size) and 28×70 mm (half size). The SMB and enclosures are laid out such that a full size card may only be installed in a full size slot but a half size card may be installed in either a full size or a half size slot.

In addition to the Systech option slots, each SysLINK 1000 through 4000 can support one or two Mini PCI Express daughter boards (PCIe). SIM sockets (or slots) may be provided, for example, on the gateway device via the PCIe board. Cellular certification is eased by mounting the cellular modem Mini PCI Express card on a carrier board that includes the Mini PCIe connector and a SIM (designed to accommodate a specific cellular module). The other Mini PCI Express slot can be used for other high speed connectivity support, such as Wi-Fi. Both of the Mini PCI Express boards communicate via a High Speed 480 Mbs USB 2.0 interface.

Typically, one end of an option card will be secured to the motherboard with a 22 pin header arranged as 2×11 on 0.10 inch centers, with the other end supported by standoffs. External connectors affixed to option cards protrude through the rear of the enclosure. Systech option card may be, for example, a simple POTS implementation.

The option card connection is made through a 20 pin header. These signals bring the host processor's SPI, I2C, USB, and UART/USART data and clock to the board. Additionally, power, ground, and interrupt request lines are present. The table below shows assigned connections. On some Systech cards, only pins 1 through 18 are available and pins 2 and 4 are not available to carry USB data. In other embodiments, a 22 pin header is used. All signal levels 3.3 V DC unless otherwise indicated.

TABLE Daughter Board Signals Option Card Pin Header Pin Signal Description 1 V+ Raw Supply Power 2 USB-M USB Port 3 V+ Raw Supply Power 4 USB-D USB Port 5 GND Ground 6 GND Ground 7 I2C - SDA I2C Data 8 I2C - CLK I2C Clock 9 3.3 V DC Regulated 3.3 V 10 3.3 V DC Regulated 3.3 V 11 TXD Serial Xmit Data 12 SPI - SCLK SPI Clock 13 RXD Serial Rev Data 14 SPI - MOSI SPI Data from Host 15 CTS Clear to Send 16 SPI - MISO SPI Data to Host 17 RTS Request to Send 18 /SPI - SEL Board Select - Active Low 19 SDC Serial Data Clock 20 /INT Interrupt Service Request 21 GND Chassis Ground 22 GND Chassis Ground

An example SysLINK gateway, designated SysLINK 3000 and illustrated in FIG. 4, has a motherboard 410 with a single Ethernet connection and a single PCIe connection 421. The SysLINK 3000 includes four option cards 451-454. The illustrated device includes an RS232 option card 453 with an extended rear portion allowing a wide DB25 connector. The adjacent option card 454 does not include external ports, for example, a security coprocessor card.

Another example SysLINK gateway, designated SysLINK 4000 and illustrated in FIG. 5, has a motherboard 510 with four Ethernet connections, divided between two separate networks; two PCIe slots 521-522 for cellular and Wi-Fi; a full size 553 and two half size 551-552 option slots that can be used for one or more Serial, POTS, GPIO, DEX, Zigbee or Z-Wave cards; and two externally visible USB connections for USB storage devices or additional connectivity options.

An integrated ARM9 processor from Atmel (AT91SAM9G45) is used in some of the models. In addition to the processing core, it includes four USB 2.0 High Speed 480 Mbs ports (particularly useful, for example, for supporting 4G and 3G at their maximum rates), embedded NAND flash control, four UART/USARTs onboard as well as a debug serial port, and advanced power management features.

Functional and/or physical isolation may be required to pass Payment Application Data Security Standard (PA-DSS) compliance testing. A gateway device may thus use an isolated payment processor. Payment data processed by the processor and resulting encrypted data can be passed via a serial port or other transport medium to the mother board. The board handles the clear text transaction recognition, Open SSL (secure sockets layer) encryption and packing and unpacking of data. This data will then be passed through the port to gateway device for communication using the gateway device's preferred connectivity hierarchy.

Some gateway devices include UPS (uninterruptible power supply) and battery backup. When the gateway device detects a slow, monotonic decrease in supply voltage, it will assume it is running on backup power and provide an alert message to the server. This message will indicate, based on the rate of voltage decay an estimated time to shutdown.

The gateway device firmware may be implemented using a standard embedded operating system, for example, Embedded Linux. When using Embedded Linux, some firmware using threads can be ported to Linux using the <pthreads.h> library. This library provides a POSIX compatible set of calls, implemented via calls to Linux kernel primitives.

Also Stream abstraction from System V, release 4 (SVR4) can be supported under Linux by LiS v2.19 (Linux Streams). This library implements the streams abstraction at the user level through multitasking. It should facilitate the porting of existing PPP/POTS transaction handling functions to new platforms. OpenSSL code may alternatively be used to address this.

A Streams interface to the 3G and 4G cards may allow code for slower networks to work seamlessly on faster cellular networks.

Gateway devices may use a streams based M2M design. One gateway may include 13 different IO modes, e.g., Ethernet, cellular, Wi-Fi, Bluetooth, ZigBee, Z-wave, DEX, MDB, motion/position, temperature, location, GPIO, and POTS. Each of those IO modes may have several associated device types. Even for a single device model on each IO, there are 156 (12×13) different cross connection combinations. Stream bridges may be used to support all possible connections. Since many of these ports have many device classes that must be handled, the practical possible combinations can be in the thousands.

Furthermore, this assumes the gateway device is not “smart.” That is to say, it does not have any semantic knowledge of the data it transports. This condition is clearly not the case in the payment processing applications, nor will it be true for many emerging applications, such as medical logging, office automation, security, and vending. Thus, firmware may be as modular, reusable, and easily validated as practically possible.

A streams model includes a hierarchical data flow architecture. The basic concepts of an example firmware architecture include:

IO Streams flow bidirectionally to and from ports.

Device Abstraction Filters (DAFs) are inserted into IO Streams. Their function is to intercept a subclass of data streaming from a Port (Upstream, or the left side of the filter) and route it to another Device Filter or API Filter. Data that is not part of a member of the device subclass is passed downstream. Data streaming from downstream of the device to the IO port is simply passed to the device filter without any handling.

DAFs may be implemented, for example, in C++. In many embodiments, DAFs pass and receive device data to or from other DAFs as XML text messages. The API of a DAF can be defined as an object class contained in a library supplied to an embedded application developer.

API Filters are connected to the Device Data port of a DAF. These object classes provide a uniform set of embedded Application Program Interfaces to Device Abstraction Filters. They regularize the method for sending data to and from a Device Abstraction and monitoring and generating device events.

Device Messaging Tasks are two port processes that pass data packets between a pair of device abstractions without any significant interpretation of the contents of those packets.

Embedded Application Tasks (EATs) are tasks attach and communicate with one to many different API filters. Any API Filter may only be attached to a single Embedded Application Task, but a single Embedded Application Task may attach many different API Filters.

EATs can be implemented in virtual machines, for example, JAVA and PHP. For procedurally complex operations, JAVA may be the preferred development platform. For simpler operations transforming EATs, PHP may be employed.

Remote JAVA debugging can be used to facilitate program development.

The firmware architecture of an example gateway device may be configured to perform multiple functions. In this example, most upstream communication is a payment processor embedded application. It takes payment requests from a local secure Ethernet or a POTS port. These payments are encrypted and communicated via a cellular connection to a payment services provider. Since they are the upstream connections to most IO streams, no data pertaining to these transactions can be visible to filters downstream and are thus secure.

The next set of filters passes location information to an OnDemand connection. Further downstream, an embedded application passes building status and handles building control commands with a remote building management server. Finally, a Wi-Fi Hotspot server provides wireless connectivity to users, but the access is filtered and access controlled by the Wi-Fi Hotspot router application.

This modular firmware architecture can be based on porting an implementation of Linux Streams to the gateway device. Additionally, software coding, interface and tasking standards can be used to assure uniformity of filter implementation and reusability of filter components and tasks in different client configurations. For example, by applying the described methods, a new customer configuration comprised of differently connected filters and tasks may require verification of the integration but not of the individual component functionality.

The gateway device may operate with a two-step boot process. The flash memory may be partitioned into a number of virtual Linux drives. For example, there can be: a Safe Boot Drive Image; a Customer Boot Drive Image; and a Data Drive Image.

The boot process can include initializing SDRAM memory and other hardware interfaces and then checking the integrity of the Customer Boot Drive Image. At a minimum, the Customer Boot image should have a good checksum, valid file structure, and a correct electronic signature. If these conditions are met, a watch dog timer will be set and an attempt will be made to boot the Customer Boot Drive Image. As part of the Customer boot process, the watch dog timer is turned off after a sufficient level of functionality has been initialized to insure that the host may be contacted and updates may be validated and downloaded with the operating kernel.

If the watch dog timer expires prior to being turned off, the system will automatically boot using the Safe Boot Drive Image. Whenever the unit boots from the Safe Boot Drive, it will contact the SOUP (using, for example, Systech Online Update Protocol) server, indicate its customer boot failure, and wait for a new customer boot image to be downloaded.

A short press of the RESET switch will trigger a reboot from the Customer Boot Drive Image. A long press of the RESET switch will trigger a reboot from the Safe Boot Drive Image.

The Safe Boot system will typically be configured to contact the Systech server and perform Customer firmware update and then reboot the system normally.

In addition to the firmware embedded in the device, external software running on other platforms may be used for some functionality. Example protocols for communication between the device and other platforms include SOUP, OnDemand, RM, and LWHB.

SOUP—uses HTTP/HTTPS to connect to a SOUP server, send status, and check for new code, configuration files, or PRL files. A unit set up for SOUP updates is typically configured to connect to the host on boot up and then daily during the night. It can also be configured to more frequently send “heartbeats” (status messages) during the day.

RM—Remote Management—provides access to the web server interface on the unit. The unit makes an outbound connection to a server, sends its MAC address to identify itself, then remains connected and waits. When a client wants to connect to the unit, it connects to the server, identifies the unit it wants to talk to, and the server connects the two sockets. At that point, the connection operates just as if the client had connected to port 80 or 443 on the unit.

OnDemand—operates similarly to RM, but gives access to a port (e.g., serial port or pots port) instead of to the web server interface.

Direct Connection—A TCP connection can be made to a physical port on the gateway device. For example, connect to TCP port 800n or 900n on the unit to talk to physical port n. Once the connection is established, the device can “write/send” data out the TCP connection to go out the port, and the device can “read/recv” data arriving on the physical port. The 800n ports support “raw TCP”—the device doesn't touch the data, just send/receive it as is. The 900n ports may support the “telnet” protocol. So the device looks for and processes telnet escape sequences in the TCP data stream and generates appropriate telnet escapes to the host.

If the device is behind a firewall (e.g., for “wired” units) or on a private network (e.g., as AT&T does for cellular units), it may not be able to make TCP connections to the ports. But with OnDemand the device can do virtually the same thing as with RM. The device makes a connection to a server, identifies itself (MAC) and the port it is offering, and then waits for some activity. When a client program wants to connect to the port, it connects to the server, asks for a MAC/port combo, and the server connects the two sockets. At that point, the connection operates just as if the client had connected to port” 800n or 900n on the unit.

RM server software may be, for example, written in python and use OpenSSL. OnDemand server software may be, for example, .NET application for Windows. The server software may have complexities to deal with security, identifying the device/port to connect to, etc. In the case of OnDemand, it is may be a paid service so that the existence of a valid license should be checked.

LWHB—Light Weight Heart Beat is a protocol. SOUP updates may be relatively costly. A daily update on a cellular unit over HTTPS consumes about 27 Kbytes of data if there are no updates. Done daily, that consumes over 800 K of data which may be on a 2-5 MB/month data plan. LWHB is designed to send a very small amount of data (about 12 bytes), unencrypted, optionally over UDP or TCP, to the host. The host can just record the contact (and the source IP address can be helpful) or it can respond with some actions—like “Do a full update”, “Send status”, “Reboot”, etc.

LWHB is designed such that users can configure their devices to not do a full update every day but do frequent LWHBs (e.g., every 30 minutes). The server side can then enable a full update only when there is something to be updated.

A gateway device may include support for connection services with a method whereby the initial IP address to which a device connects, can redirect the unit to another IP address. This allows an initial connection server to offload connections to many different servers. The connection server may use a networked backend database to track what units are attached to servers at any given time so that it can perform load balancing. Additionally, customer clients may initially connect to the connectivity server, but they may subsequently be redirected to the server where the corresponding device is waiting.

The connection server method allows protocols to scale by allowing additional servers to be added or deleted as necessary.

The LWHB may be extended to allow the host to inform the unit that it has been requested to attach to the RM or OnDemand server. When it receives this request, it can be connected to a server and remain attached for up to one heart beat interval awaiting a connection from its client. Once, the requested unit has connected to the server, the server will notify the client via email, IM, other protocol messages, or a combination thereof. The client can then connect to the unit via OnDemand or RM and complete whatever activity is required. Furthermore, the LWHB protocol may allow that units can post that some actionable alarm or warning condition (e.g., exceeding a temperature, location, motion range, or some other fencing condition) has occurred. In this case the unit will immediately connect to the OnDemand or RMs server and await service from its client.

The above methods reduce connection stresses on OnDemand and RM servers. By not remaining continuously connected to the servers, many more units can be handled. The cost of this is the latency of a server responding to client request. For most automated clients, a cadence measured in hours, is likely sufficient for routine operations.

LWHB servers may also include data archiving and retrieval. The data may, for example, be accessed by customer applications use an XML schema for data to be stored and retrieved on their behalf on backend database servers.

GPS and AGPS data can be received from the unit by the client, either directly or via a host. The GPS port can use the NEMA ASCII standard to send the location, time and motion information. The NEMA sequence, in an implementation, repeats once per second. The information can be packaged in an XML wrapper.

Temperature data can be forwarded, for example, as ASCII strings including the sensor number followed by a space followed by the Celsius temperature as an ASCII expressed real number followed by a linefeed. If a temperature limit has been exceeded, the word “ALERT” may be appended to the sensor string. For example:

1 27.5C

2 33.9C ALERT

In one implementation, the sequence repeats every 10 seconds and is packaged in an XML wrapper.

The Position and motion sensor report can, for example, return a string containing the instantaneous acceleration and forces in the X, Y, and Z axis followed by the time and maximum changes in X, Y and Z forces over the past 24 hours. The forces are ASCII expressed real numbers that are in units of Gs and are packaged in an XML, wrapper. This string will repeat at a low rate unless a fence has been violated in which case its cadence is increased.

An example of a stable unit might be:

0.1 0.02 0.97 0.01 0.01 0.01

A unit that has been tampered might return:

0.1 0.05 0.78 0.4 0.5 1.0

A power monitoring report can include, for example, a string of four ASCII expressed numbers separated by spaces and packaged in an XML wrapper. These may report the current supply voltage, the rate of change of the supply voltage over the last 30 minutes expressed in volts per hour, the peak supply voltage in the past 24 hours, and the minimum voltage in the last 24 hours.

An example of a stable UPS powered unit might return:

13.50 +0.05 13.56 13.44

A UPS powered unit experiencing a power failure might return

11.60 −1.17 13.55 11.60

A system may also create and transmit DEX fault reports.

In a further example system, text messaging is used as a way to view and manage cellular gateway device units. There are multiple ways that text messaging can be utilized in conjunction with gateway device products.

Unit status—a user can text the serial number of a unit to a service number and get back the status for the unit having that service number. Example status includes the last time the unit contacted SOUP and other useful info about the unit. Relatively benign information (not exposing anything private about the unit) may be provided, in an implementation, without requiring any authentication or registration. Other information can be more private (e.g., the current IP address, configuration information, etc.). Such information may require the requester to have previously registered her phone number in a SOUP account before access is allowed.

Status information may be supplied without communicating with the gateway device unit by supplying information stored at the server. SMS messages to the server can also schedule a reboot, update, etc.

Commands to the unit—A gateway device unit may be capable of receiving SMS (text) messages. The SMS messages may contain commands to the unit. The commands generally require secure verification of the source of the command. Accordingly, the gateway device unit may include authentication and encryption functionality.

Status from the unit—A gateway device unit may also be capable of sending SMS messages. In some situations, SMS messaging may be available when other cellular connectivity is unavailable. Accordingly, the gateway device unit may send SMS messages for certain alerts, for example, an alert text message indicating an inability to connect to a server.

Those of skill will appreciate that the various illustrative logical blocks, modules, units, and algorithm steps described in connection with the embodiments disclosed herein can often be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular constraints imposed on the overall system. Skilled persons can implement the described functionality in varying ways for each particular system, but such implementation decisions should not be interpreted as causing a departure from the scope of the invention. In addition, the grouping of functions within a unit, module, block, or step is for ease of description. Specific functions or steps can be moved from one unit, module, or block without departing from the invention.

The various illustrative logical blocks, units, steps and modules described in connection with the embodiments disclosed herein can be implemented or performed with a processor, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm and the processes of a block or module described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium. An exemplary storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. Additionally, device, blocks, or modules that are described as coupled may be coupled via intermediary device, blocks, or modules. Similarly, a first device may be described a transmitting data to (or receiving from) a second device when there are intermediary devices that couple the first and second device and also when the first device is unaware of the ultimate destination of the data.

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles described herein can be applied to other embodiments without departing from the spirit or scope of the invention. Thus, it is to be understood that the description and drawings presented herein represent a presently preferred embodiment of the invention and are therefore representative of the subject matter that is broadly contemplated by the present invention. It is further understood that the scope of the present invention fully encompasses other embodiments that may become obvious to those skilled in the art and that the scope of the present invention is accordingly limited by nothing other than the appended claims. 

What is claimed is:
 1. A method of improving signal reliability of a cellularly-connected host device, comprising: monitoring, by a host device, a signal reliability of a cellular module for a signal reliability event; detecting, by the host device, the signal reliability event based on the monitored signal reliability reaching an event threshold; providing data regarding the signal reliability event to a remote server; receiving, by the remote server, the data regarding the signal reliability event; upon the detection of the signal reliability event, performing, by the host device, each of the following steps: issuing a command to the cellular module to re-establish connection with a first cellular network; and restarting the cellular module; accumulating the data regarding the signal reliability with previously received data regarding prior signal reliability; adjusting, by the remote server, the event threshold based on the accumulated data; transmitting, by the remote server, the adjusted event threshold to the host device; and updating, by the host device, the event threshold based on the received adjusted event threshold; wherein a modem provides cellular communications capabilities to the host device.
 2. The method of claim 1, wherein the signal reliability comprises at least one of a viability of network connection, a signal strength, a signal quality, or a signal delay.
 3. The method of claim 1, wherein providing the data regarding the signal reliability event to the remote server further comprises providing at least one of a cellular module identifier, a SIM card identifier, a host device identifier, and a modem identifier.
 4. The method of claim 3, wherein the cellular module identifier comprises at least one of an IMEI number or an IMSI number.
 5. The method of claim 7, wherein the SIM card identifier is an ICCID.
 6. The method of claim 1, further comprising: sending, by the modem, device data over a first link; characterizing, by the host device, the signal reliability event as the data regarding the signal reliability event; and sending the data regarding the signal reliability event to the remote server.
 7. The method of claim 6, wherein a first link and a second link are operated simultaneously and wherein operating the second link does not interfere with the operation of the first link.
 8. The method of claim 6, further comprising changing transmission of device data from sending over the first link to sending over a second link.
 9. The method of claim 6, further comprising encrypting the device data, and sending the encrypted device data over the second link.
 10. The method of claim 6, wherein the signal reliability data is encrypted prior to sending, and wherein sending encrypted signal reliability event data to the remote server comprises authenticating the host device with the remote server.
 11. The method of claim 6, further comprising encrypting at least one of the signal reliability event data and the device data.
 12. The method of claim 6, wherein the device data is sent to an external server.
 13. The method of claim 1, further comprising providing a modem that coupled to the cellular module and a processor.
 14. A system comprising: a host device comprising a cellular module and a processor configured to perform the logical functions of: monitoring signal reliability of the cellular module for a signal reliability event; providing the signal reliability event to a remote server; upon detection of the signal reliability event, perform each the following steps: issuing a command to the cellular module to re-establish connection with a first cellular network; and restarting the cellular module; and the remote server configured to perform the logical functions of: accumulating the data regarding the signal reliability event with previously received data regarding prior signal reliability events; adjusting an event threshold based on the accumulated data; and transmitting the adjusted event threshold to the host device; and the host device further configured to perform the logical function of updating the event threshold based on the received adjusted event threshold.
 15. A method of improving signal reliability of a cellularly-connected host device, comprising: monitoring a signal reliability of a cellular module for a signal reliability event; detecting the signal reliability event based on the monitored signal reliability reaching an event threshold; providing data regarding the signal reliability event to a remote server; upon the detection of the signal reliability event, performing each of the following steps: issuing a command to the cellular module to re-establish connection with a first cellular network; and restarting the cellular module; accumulating the data regarding the signal reliability with previously received data regarding prior signal reliability; adjusting the event threshold based on the accumulated data; and updating the event threshold based on the received adjusted event threshold; wherein a modem provides cellular communications capabilities to the host device. 